License Manager Usage Logs

Customer-defined log file encryption level as specified by the License Manager -lfe option. See Encrypting License Manager Log File Entries.

Vendor-defined log file encryption level. If this is non-zero, it overrides the Server-LFE.

The date and time at which the usage log entry is made in the format: Day-of-week Month Date Time (hh:mm:ss) Year

The time stamp at which the usage log entry is made.

Product feature name.

Product version name.

The transaction types are categorized and described below:

Explicit Entries:

• 0 - A license is issued.
• 1 - A license is denied.
• 2 - The License Manager has released the issued key for which no update was received from client application.
• 3 -  A queued key is issued and the client is placed in a queue. When the license would be available (after other clients release any token), this client may get that license.
• 4 - The queuing request failed.
• 5 - The queuing request succeeded, however, instead of obtaining a queued key the client receives the normal key and is not placed in the queue.
• 6 - A queued license is converted to an actual license. This happens when the client obtains the license that was released by some other client (and a queued client may call the VLSgetQueuedClient API to get the key). Thereafter, the client is removed from the queue.
• 7 - A queued license key that was issued earlier is released as it could not be converted into an actual license key (non-queued key) after a certain time period.
• 8 - A commuter license is checked out.
• 9 - A commuter license is checked in.

Implicit Entries:

• 10 - Implicit license release entry when the License Manager performs cleanup of in use keys before shutdown.
• 11 - Implicit license release entry when the License Manager reclaims tokens after the key lifetime period has expired.
• 12 - Implicit license release entry when any of the following transactions takes place:
• License A is released at midnight when license switches to License B.
• Or, the license is released after actual revocation takes place for a deferred revocation case.
• Or, License A is released when License B is dynamically added.
• 13 - Implicit license release entry when the usage log file is changed under any of the following scenarios:
• When the backup usage log file is created (in case of overflow), a license release entry in the backup log file.
• When the log file is changed by calling the VLSchangeUsageLogFileName API, a license release entry in the previous log file.

• 14 - Implicit license request entry under the scenarios when update calls are converted into request. For example:
• When clients are running and the heartbeat message is sent after the License Manager restart
• When heartbeat messages are sent after the key lifetime expiration
• 15 - Implicit license request entry under any of the following scenarios:
• When the backup usage log file is created (in case of overflow), a license request entry in the new log file.
• When the log file is changed by calling the VLSchangeUsageLogFileName API, a license request entry in the new log file.
• 16 - Implicit release entries in the usage log file of the follower server, when the original leader comes back after going down (in the case of redundant License Manager setup).

The number of licenses in use after the current request/release. (Encrypted if encryption level is set to 3 or 4.)

For how long (in seconds) the license was in use. Only applicable in a license release entry.

The user name of the application associated with the entry. This element can be logged anonymously if the anonymous logging option is set.

The host name of the application associated with the entry. This element can be logged anonymously if the anonymous logging option is set.

The version of the License Manager.

The number of licenses handled during the transaction. (Encrypted if encryption level is set to 3 or 4.)

The data passed in by the vendor's licensed application. This element can be logged anonymously if the License Manager anonymous logging option is set and vendor has allowed anonymization of comments in the licensed application.

The comment can be fully or partially anonymized depending on the vendor's implementation.

License Manager's startup messages.

(Server-LFE) Customer-defined log file encryption level.

2 is the default level for encrypting log file entries (see description below in the next section).

(License-LFE) Vendor-defined log file encryption level.

3 means that vendor has allowed encryption of usage data. Transaction data will be readable other than license usage data can be displayed by lsusage.

The log file encryption level 3 will override any level set by the customer.

(Date) Date and time at which the license transaction was made.

(Time-stamp) Time-stamp of the transaction record.

This timestamp represents the time of creation of the log entry.

(Feature/Ver) Feature name a and 2 version for the first license.

4 is both the feature name and version for the second license.

(Trans) The transaction ID.

0 denotes that a license was granted.

15 denotes an implicit license request entry as per the scenario described in the transaction ID #15 above.

(Numkeys) 1 token was in use after the request.

(Keylife) Only applicable for a license release.

(User) The user requesting the license.

(Host) The host name of the computer on which the license request was made.

(LSver) The License Manager version.

(Currency) The number of license requested for that key. Only 1 license was handled in both the transactions.

Allows no encryption. Transaction data will be logged for this license code with no encryption.

No encryption, tags each record with checksum. Transaction data will be readable by the customer, but tampering with or deleting an entry can be detected if the appropriate usage utility (lsusage) is run on the log file.

Encrypt usage only. Transaction data will be readable by the customer except for license usage data (which will be encrypted), but tampering with or deleting an entry can be detected if the appropriate usage utility (lsusage or vusage) is run on the log file.

Encrypt entire record. All transaction data for the license code will be encrypted. Tampering with or deleting an entry will not be prevented, but can be detected if the appropriate usage utility (lsusage) is run on the log file.